build(deps): bump github.com/influxdata/flux #2796
Open
+50
−21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@stefanb maybe let's try including this patch and upgrading kapacitor to 1.7.1 on the homebrew side? what do you think? |
|
Not sure, the CI didn't pass here. |
6 tasks
bump github.com/influxdata/flux from v0.171.0 to v0.191.0 Fixes influxdata#2769 There are also newer releases that could be used: https://github.com/influxdata/flux/releases
|
fix pr, #2811 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
bump github.com/influxdata/flux from v0.171.0 to v0.191.0
Fixes #2769
There are also newer releases that could be used: https://github.com/influxdata/flux/releases
Required checklist
/etcfolder andNewDemoConfigmethods) (influxdb and plutonium)Description
1-3 sentences describing the PR (or link to well written issue)
Context
Why was this added? What value does it add? What are risks/best practices?
Affected areas (if applicable):
List of user-visible changes. As a user, what would I need to see in docs?
Examples:
CLI commands, subcommands, and flags
API changes
Configuration (sample config blocks)
Severity (optional)
i.e., ("recommend to upgrade immediately", "upgrade at your leasure", etc.)
Note for reviewers:
Check the semantic commit type: